Elicitation and Specification Processes of NFR for Web Applications

The notion of Non Functional Requirement (NFR) of software system is not homogeneous. There is lack of consensus to answer questions as: What are they? How do they classify within the software development context? Also, knowing, how there are classified in the Web application development? In [1] we compared six Methodological approaches used for the development of Web applications in order to analyze how these approaches treat to Non-Functional Requirements (NFR); we conclude that: NFR are considered, but there is no consensus in their meaning. There are neither specifics techniques for elicitation of NFR Web nor uniform guidelines for the specification and validation. Some of the studied methodologies have tools to deal with NFR but they are specific to the process they support. There is a lack of consensus to establish within which phase of development lifetime cycle NFR are identified. The maturity of the Requirements Engineering process related to NFR seems insufficient to develop such applications. To overcome this shortcoming in the proper treatment of NFR demands new approaches or evolve the current approaches. Due to its importance, activities to capture, specification and validation of Web’s NFR, must have specific guidelines and techniques for them. This work introduces processes to Elicitation and Specification of Web Applications NFR (quality and restrictions) using templates especially designed to capture and NFR specify. The proposed notions and processes are validated in a real project.